stardust-xr-gravity: 0-unstable-2024-12-29 -> 0.51.0-unstable-2026-03-19#466340
stardust-xr-gravity: 0-unstable-2024-12-29 -> 0.51.0-unstable-2026-03-19#466340r-ryantm wants to merge 1 commit intoNixOS:masterfrom
Conversation
|
Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript. meta.description for stardust-xr-gravity is: Utility to launch apps and stardust clients at an offet meta.homepage for stardust-xr-gravity is: https://stardustxr.org Updates performed
To inspect upstream changesImpactChecks done
Rebuild report (if merged into master) (click to expand)Instructions to test this update (click to expand)Either download from the cache: (The nixpkgs-update cache is only trusted for this store-path realization.) Or, build yourself: Or: After you've downloaded or built it, look at the files and if there are any, run the binaries: Pre-merge build resultsWe have automatically built all packages that will get rebuilt due to This gives evidence on whether the upgrade will break dependent packages.
|
cc48efa to
0a31c26
Compare
Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for stardust-xr-gravity is: Utility to launch apps and stardust clients at an offet
meta.homepage for stardust-xr-gravity is: https://stardustxr.org
Updates performed
To inspect upstream changes
Impact
Checks done
passthru.tests, if any, passedRebuild report (if merged into master) (click to expand)
Instructions to test this update (click to expand)
Either download from the cache:
(The nixpkgs-update cache is only trusted for this store-path realization.)
For the cached download to work, your user must be in the
trusted-userslist or you can usesudosince root is effectively trusted.Or, build yourself:
Or:
After you've downloaded or built it, look at the files and if there are any, run the binaries:
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-reviewresultGenerated using
nixpkgs-review.Command:
nixpkgs-review --extra-nixpkgs-config '{ allowBroken = false; }'Commit:
cc48efa997fdb2a789404e5b73fdb0cce2c3baf8x86_64-linux✅ 1 package built:
Maintainer pings
cc @Pandapip1 @technobaboo for testing.
Tip
As a maintainer, if your package is located under
pkgs/by-name/*, you can comment@NixOS/nixpkgs-merge-bot mergeto automatically merge this update using thenixpkgs-merge-bot.Add a 👍 reaction to pull requests you find important.